Linked.Archi Backstage Cross-Language Mappings

Linked.Archi Backstage Cross-Language Mappings: Overview back to ToC

This ontology has the following classes and properties.

Annotation Properties

• close match
• creator
• description
• issued
• license
• modified
• preferred namespace prefix
• preferred namespace uri
• related match
• source
• title

Linked.Archi Backstage Cross-Language Mappings: Description back to ToC

Cross-language SKOS mappings between Backstage Software Catalog kinds and relations and ArchiMate modeling language concepts, for both ArchiMate 3.2 and ArchiMate 4.0. These mappings are editorial. Backstage documents its catalog model without reference to ArchiMate, and the ArchiMate specification does not mention developer portals. The assertions here express semantic proximity based on the kind definitions in the Backstage catalog model and the concept definitions in the ArchiMate specifications. The catalog describes software as it is owned and operated: what is deployed, who owns it, which APIs it exposes, what infrastructure it needs. ArchiMate describes the same estate at an architectural grain. The closest fit is at the application layer — a Backstage System and an ArchiMate application component are both the unit that architects and owners reason about — so that pair is skos:closeMatch. Elsewhere the kinds are deliberately broad (a Resource can be a database, a bucket, a server or a cluster; a Domain is any grouping) and the mappings are skos:relatedMatch, fanning out to each ArchiMate concept a modeller might choose. These are type-level statements. They do not say that any particular catalog entity corresponds to any particular ArchiMate element; instance-level correspondence is asserted in the catalog itself, through the Linked.Archi catalog index (skos:exactMatch and friends against a shared id namespace). Not mapped, deliberately: bs:Template and bs:Scaffolding (they describe how entities are created, not the architecture), bs:TechDocsDelegation (documentation ownership), and the enumerations for lifecycle, component type and API type, which are reference data rather than concepts.

Cross-reference for Linked.Archi Backstage Cross-Language Mappings classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi Backstage Cross-Language Mappings.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.